docs(airplay): point pair_probe at #27 rather than the split-up #8 - #38
Merged
Conversation
#8 bundled two unrelated problems and was closed when #28 split it: the FairPlay half became a settled decision recorded in `docs/crypto.md`, and the half that is still open — whether HAP transient pairing works against real hardware — became #27. `pair_probe` exists solely to answer that open half, but both its module doc and the failure hint it prints still cite #8, so anyone following the pointer lands on a closed issue whose FairPlay half is explicitly out of scope.
snadahalli
force-pushed
the
docs/pair-probe-issue-refs
branch
from
August 26, 2026 09:38
c8b37f7 to
f5765e7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#8 bundled two unrelated problems and was closed when #28 split it: the FairPlay half became a settled decision recorded in
docs/crypto.md, and the half that is still genuinely open — whether HAP transient pairing works against real hardware — became #27.pair_probeexists solely to answer that open half, but both its module doc (line 4) and the failure hint it prints (line 107) still cite #8. Anyone following the pointer lands on a closed issue whose FairPlay half is explicitly out of scope.Two string changes, no behaviour.